CI Results for PR #88 (use LaMEM_jll 2.2.0) from Claude Code after reading every log output

Pass/Fail Matrix

Two Distinct Failure Modes

Failure 1: CairoMakie precompilation crash (Julia 1.12 only)

Affects: All 3 Julia 1 (= 1.12) jobs (Ubuntu, macOS Intel, Windows)

CairoMakie fails to precompile because MakieCore accesses Core.TypeName.mt, a field that was removed in Julia 1.12. Tests never run at all.

FieldError: type Core.TypeName has no field `mt`

This is a Makie ecosystem incompatibility with Julia 1.12 — not a LaMEM bug.

Failure 2: run_lamem_save_grid returns nothing (all macOS, all Julia versions)

Affects: All 4 macOS jobs (Intel + ARM, Julia 1.10 + 1.11) — macOS-specific

The same error hits 4 test sets on every macOS runner:

Test Set: run lamem mode save grid test
Error: MethodError: no method matching length(::Nothing)
────────────────────────────────────────
Test Set: filesize compression
Error: MethodError: no method matching length(::Nothing)
────────────────────────────────────────
Test Set: Subduction3D (example script)
Error: MethodError: no method matching length(::Nothing)
────────────────────────────────────────
Test Set: TM_Subduction_example (example script)
Error: MethodError: no method matching length(::Nothing)

All 4 share the same root cause — run_lamem_save_grid() at src/run_lamem_save_grid.jl:92 returns nothing when it should return something with a length. The call to length() on that nothing then crashes.

This means run_lamem_save_grid is failing silently on macOS — likely the LaMEM binary (from LaMEM_jll 2.2.0) isn't producing the expected grid output on macOS, so the function returns nothing instead of valid data.

33 tests pass on macOS — it's only the tests that go through run_lamem_save_grid that fail.

Summary

The macOS-specific failure in run_lamem_save_grid is the one directly related to this PR's change (updating LaMEM_jll to 2.2.0). I'd suggest investigating what run_lamem_save_grid at src/run_lamem_save_grid.jl:92 expects to return and why the new LaMEM_jll 2.2.0 binary behaves differently on macOS.